Load/Move and Duplicate Instructions for a Processor

ABSTRACT

A method includes, in a processor, loading/moving a first portion of bits of a source into a first portion of a destination register and duplicate that first portion of bits in a subsequent portion of the destination register.

CLAIM TO PRIORITY

The present application is a continuation of U.S. patent application Ser. No. 13/620,194, entitled “LOAD/MOVE AND DUPLICATE INSTRUCTIONS FOR A PROCESSOR” filed on Sep. 14, 2012, which is a continuation of U.S. patent application Ser. No. 13/494,764, entitled “LOAD/MOVE DUPLICATE INSTRUCTIONS FOR A PROCESSOR” filed on Jun. 12, 2012, which is a continuation of U.S. patent application Ser. No. 13/088,198, filed on Apr. 15, 2011, entitled “LOAD/MOVE DUPLICATE INSTRUCTIONS FOR A PROCESSOR”, now U.S. Pat. No. 8,200,941, Issued on Jun. 12, 2012, which is a continuation of U.S. patent application Ser. No. 12/940,782, filed on Nov. 5, 2010, entitled “LOAD/MOVE DUPLICATE INSTRUCTIONS FOR A PROCESSOR”, now U.S. Pat. No. 8,032,735, Issued on Oct. 4, 2011, which is a continuation of U.S. patent application Ser. No. 10/032,144, filed on Dec. 20, 2001, entitled “LOAD/MOVE AND DUPLICATE INSTRUCTIONS FOR A PROCESSOR”, now U.S. Pat. No. 7,853,778, Issued on Dec. 14, 2010, all of which are hereby incorporated herein by reference.

TECHNICAL FIELD

This invention relates to load/move and duplicate instructions for a processor.

BACKGROUND

A system architecture describes the mode of operation of a processor and mechanisms provided to support operating systems and including system-oriented registers and data structures and system-oriented instructions. The system architecture also provides the mechanisms necessary for switching between real-address and protected modes.

Introduction of a single-instruction, multiple-data (SIMD) technology to a system architecture provides for parallel computations on packed integer data contained in 64-bit registers. SIMD provides enhanced performance to a processor in, for example, advanced media, image processing and data compression applications.

DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of a processor.

FIG. 2 is a block diagram of an executive environment.

FIG. 3 is a diagram of a byte order fundamental data type.

FIG. 4 shows a floating-point format.

FIG. 5 shows a table summarizing the various SIMD extensions, data types and how the data types are packed into registers.

FIG. 6 illustrates operations that may be performed according to one embodiment of the invention.

DETAILED DESCRIPTION

Referring to FIG. 1 a processor 10 is shown. The processor 10 is a three way super scaler, pipelined architecture. Using parallel processing techniques, the processor 10 is able on average to decode, dispatch, and complete execution of (retire) three instructions per clock cycle. To handle this level of instruction throughput, the processor 10 uses a decoupled, twelve stage pipeline that supports out of order instruction execution. The micro architecture pipeline of the processor 10 is divided into four sections, i.e., a first level cache 12 and a second level cache 14, a front end 16, an out of order execution core 18, and a retire section 20. Instructions and data are supplied to these units through a bus interface unit 22 that interfaces with a system bus 24. The front end 16 supplies instructions in program order to the out of order core 18 that has very high execution bandwidth and can execute basic integer operations with one-half clock cycle latency. The front end 16 fetches and decodes instructions into simple operations called micro-ops (μ-ops). The front end 16 can issue multiple μ-ops per cycle, in original program order, to the out of order core 18. The front end 16 performs several basic functions. For example, the front end 16 performs prefetch instructions that are likely to be executed, fetch instructions that have not already been prefetched, decode instructions into micro operations, generates micro code for complex instructions and special purpose code, delivers decoded instructions from an execution trace cache 26, and predicts branches using advanced algorithms in a branch prediction unit 28.

The front end 16 of the processor 10 is designed to address some common problems in high speed, pipelined microprocessors. Two of these problems, for example, contribute to major sources of delays. These are the time to decode instructions fetched from the target and wasted decode bandwidth due to branches or branch target in the middle of cache lines.

The execution trace cache 26 addresses both of these issues by storing decoded instructions. Instructions are fetched and decoded by a translation engine (not shown) and built into sequences of μ-ops called traces. These traces of μ-ops are stored in the trace cache 26. The instructions from the most likely target of a branch immediately follow the branch without regard for continuity of instruction addresses. Once a trace is built, the trace cache 26 is searched for the instruction that follows that trace. If that instruction appears as the first instruction in an existing trace, the fetch and decode of instructions 30 from the memory hierarchy ceases and the trace cache 26 becomes the new source of instructions.

The execution trace cache 18 and the translation engine (not shown) have cooperating branch prediction hardware. Branch targets are predicted based on their linear addresses using Branch Target Buffers (BTBS) 28 and fetched as soon as possible. The branch targets are fetched from the trace cache 26 if they are indeed cached there; otherwise, they are fetched from the memory hierarchy. The translation engine's branch prediction information is used to form traces along the most likely paths.

The core 18 executes instructions out of order enabling the processor 10 to reorder instructions so that if one μ-op is delayed while waiting for data or a contended execution resource, other μ-ops that are later in program order may proceed around it. The processor 10 employs several buffers to smooth the flow of T-ops. This implies that when one portion of the pipeline experiences a delay, that delay may be covered by other operations executing in parallel or by the execution of μ-ops which were previously queued up in a buffer.

The core 18 is designed to facilitate parallel execution. The core 18 can dispatch up to six μ-ops per cycle; note that this exceeds the trace cache 26 and retirement 20 μ-op bandwidth. Most pipelines can start executing a new μ-op every cycle, so that several instructions can be processed any time for each pipeline. A number of arithmetic logical unit (ALU) instructions can start two per cycle, and many floating point instructions can start one every two cycles. Finally, μ-ops can begin execution, out of order, as soon as their data inputs are ready and resources are available.

The retirement section 20 receives the results of the executed μ-ops from the execution core 18 and processes the results so that the proper architectural state is updated according to the original program order. For semantically correct execution, the results of instructions are committed in original program order before it is retired. Exceptions may be raised as instructions are retired. Thus, exceptions cannot occur speculatively. They occur in the correct order, and the processor 10 can be correctly restarted after execution.

When a μ-op completes and writes its result to the destination, it is retired. Up to three μ-ops may be retired per cycle. A ReOrder Buffer (ROB) (not shown) in the retirement section 20 is the unit in the processor 10 which buffers completed μ-ops, updates the architectural state in order, and manages the ordering of exceptions.

The retirement section 20 also keeps track of branches and sends updated branch target information to the BTB 28 to update branch history. In this manner, traces that are no longer needed can be purged from the trace cache 26 and new branch paths can be fetched, based on updated branch history information.

Referring to FIG. 2, an execution environment 50 is shown. Any program or task running on the processor 10 (of FIG. 1) is given a set of resources for executing instructions and for storing code, data, and state information. These resources make up the execution environment 50 for the processor 10. Application programs and the operating system or executive running on the processor 10 use the execution environment 50 jointly. The execution environment 50 includes basic program execution registers 52, an address space 54, Floating Point Unit (FPU) registers 56, multimedia extension registers (MMX) 58, and SIMD extension (SSE and SSE2) registers 60.

Any task or program running on the processor 10 can address a linear address base 54 of up to four gigabytes (2³² bytes) and a physical address space of up to 64 gigabytes (2³⁶ bytes). The address space 54 can be flat or segmented. Using a physical address extension mechanism, a physical address space of 2³⁶⁻¹ can be addressed.

The basic program execution registers 52 include eight general purpose registers 62, six segment registers 64, an EFLAGS register 66, and an EIP (instruction pointer) register 68. The basic program execution registers 52 provide a basic execution environment in which to execute a set of general purpose instructions. These instructions perform basic integer arithmetic on byte, word, and doubleword integers, handle program flow control, operate on bit and byte strengths, and address memory.

The FPU registers 56 include eight FPU data registers 70, an FPU control register 72, a status register 74, an FPU instruction pointer register 76, an FPU operand (data) pointer register 78, an FPU tag register 80 and an FPU op code register 82. The FPU registers 56 provide an execution environment for operating on single precision, double precision, and double extended precision floating point values, word-, doubleword, and quadword integers, and binary coded decimal (BCD) values.

The eight multimedia extension registers 58 support execution of single instruction, multiple data (SIMD) operations on 64-bit packed byte, word, and doubleword integers.

The SIMD extension (SSE and SSE2) registers 60 include eight extended multimedia (XMM) data registers 84 and an MXCSR register 86. The SIMD extension (SSE and SSE2) registers 60 support execution of SIMD operations on 128-bit packed single precision and double precision floating point values and on 128-bit packed byte, word, doubleword and quadword integers.

A stack (not shown) supports procedure or subroutine calls and the passing of parameters between procedures or subroutines.

The general purpose registers 62 are available for storing operands and pointers. The segment registers 64 hold up to six segment selectors. The EFLAGS (program status and control) registers 66 report on the status of a program being executed and allows limited (application program level) control of the processor. The EIP (instruction pointer) register 68 contains a 32-bit pointer to the next instruction to be executed.

The 32-bit general purpose registers 62 are provided for holding operands for logical and arithmetic operations, operands for address calculations, and memory pointers. The segment registers 64 hold 16-bit segment selectors. A segment selector is a special pointer that identifies a segment in memory. To access a particular segment in memory, the segment selector for that segment must be present in the appropriate segment register 64.

When writing application code, programmers generally produce segment selectors with assembler directives and symbols. The assembler and other tools then generate the actual segment selector values associated with these directives and symbols. If writing system code, programmers may need to generate segment selectors directly.

How segment registers 64 are used depends on the type of memory management model that the operating system or executive is using. When using a flat (unsegmented) memory model, the segment registers 64 are loaded with segment selectors that point to overlapping segments, each of which begins at address zero on the linear address space. These overlapping segments then include the linear address space for the program. Typically, two overlapping segments are defined: one for code and another for data and stacks. The CS segment register (not shown) of the segment registers 64 points to the code segment and all other segment registers point to the data and stack segment.

When using a segmented memory model, each segment register 64 is ordinarily loaded with a different segment selector so that each segment register 64 points to a different segment within the linear address space. At any time, a program can thus access up to six segments in the linear address space. To access a segment not pointed to by one of the segment registers 64, a program first loads the segment selector to be accessed into a segment register 64.

The 32-bit EFLAGS register 66 contains a group of status flags, a control flag, and a group of system flags. Some of the flags in the EFLAGS register 66 can be modified directly, using special purpose instructions. There are no instructions that allow the whole register 66 to be examined or modified directly. However, the following instructions can be used to move groups of flags to and from the procedure stacks or general purpose register: LAHF, SAHF, push-F, push-FD, pop-F, and pop-FD. After the contents of EFLAGS register 66 have been transferred to the procedure stack or a general purpose register, the flags can be examined and modified using the processor 10 bit manipulation instructions.

When suspending a task, the processor 10 automatically saves the state of the EFLAGS register 66 in the task state segment (TSS) (not shown) for the task being suspended. When binding itself to a new task, the processor 10 loads the EFLAGS register 66 with data from the new tasks program state register (PSS, not shown).

When a call is made to an interrupt or an exception handler procedure the processor 10 automatically saves the state of the EFLAGS register 66 on the procedure stack. When an interrupt or exception is handled with a task switch, the state of the EFLAGS register 66 is saved on the TSS for the task being suspended.

The fundamental data types used in the processor 10 are bytes, words, doublewords, quadwords and double quadwords. A byte is eight bits, a word is two bytes (16-bits), a doubleword is four bytes (32-bits), a quad word is eight bytes (64-bits), and a double quadword is sixteen bytes (128-bits).

Referring to FIG. 3, a byte order of each of the fundamental data types when referenced as operands in memory is shown. The low byte (bits 0-7) of each data type occupies the lowest address in memory and that address is also the address of the operand.

Words, doublewords and quadwords do not need to be aligned in memory on natural boundaries. The natural boundaries for words, doublewords and quadwords are even numbered addresses, addresses evenly divisible by 4, and addresses evenly divisible by 8, respectively. However, to improve the performance of programs, data structures (especially stacks) should be aligned on natural boundaries whenever possible. The reason for this is that the processor 10 requires two memory accesses to make an unaligned memory access, whereas aligned accesses require one memory access. A word or double-word operand that crosses a 4 byte boundary or a quadword operand that crosses an 8 byte boundary is considered unaligned and requires two separate memory bus cycles to access it. A word that starts on an odd address but does not cross a word boundary is considered aligned and can still be accessed in one bus cycle.

Some instructions that operate on double quadwords require memory operands to be aligned on a natural boundary. These instructions generate a general protection exception (#GP) if an unaligned operand is specified. A natural boundary for a double quadword is any address evenly divisible by 16. Other instructions that operate on double quadwords permit unaligned access without generating a general protection exception, however, additional memory bus cycles are required to access unaligned data from memory.

Although bytes, words and doublewords are the fundamental data types of the processor 10, some instructions support additional interpretation of these data types to allow operations to be performed on numeric data types. For example, the processor 10 defines two types of integers: unsigned and signed. Unsigned integers are ordinary binary values ranging from zero to the maximum positive number that can be encoded in the selected operand size. Signed integers are two's complement binary values that can be used to represent both positive and negative integer values.

The processor 10 defines and operates on three floating point data types: signal precision floating point, double precision floating point, and double extended precision floating point. The data formats for these data types correspond directly to format as specified in the IEEE standard 754 for binary floating point arithmetic.

Pointers are addresses of locations in memory. The processor 10 defines two types of pointers: a near pointer (32-bits) and a far pointer (48-bits). A near pointer is a 32-bit offset (also called an effective address) within a segment. Near pointers are used for all memory references in a flat memory model or for references in a segmented model when the identity of the segment being accessed is implied. A far pointer is a 48-bit logical address, consisting of a 16-bit segment selector and a 32-bit offset. Far pointers are used for memory references and a segmented memory model where the identity of a segment being accessed must be specified explicitly.

A bit field is a continuous sequence of bits. It can begin at any bit position of any byte in memory and can contain up to 32-bits. Strings are continuous sequences of bits, bytes, words or doublewords. A bit string can begin at any bit position of any byte and can contain up to 2³²⁻¹ bits. A byte string can contain bytes, words or doublewords and can range from zero to 2³²⁻¹ bytes (four gigabytes).

Binary coded decimal integers (BCD integers) are unsigned four-bit integers with valid values ranging from 0 to 9. The processor 10 defines operations on BCD integers located in one or more general purpose registers 62 or in one or more FPU registers 56.

Referring to FIG. 4, real numbers are represented in a floating point format 100 in the FPU 56 floating point registers 70. The floating point format includes three parts, i.e., a sign 102, a significant 104 and an exponent 106. The sign 102 is a binary value that indicates whether the number is positive (0) or negative (1). The significant 104 has two parts: a 1-bit binary integer (also referred to as a J-bit) 108 and a binary fraction 110. The integer-bit 108 is often not represented, but instead is an implied value. The exponent 106 is a binary integer that represents a base-2 power that the significant 104 is multiplied by.

The processor 10 defines and operates on a set of 64-bit and 128-bit packed data types for use in SIMD operations. These data types include fundamental data types (packed bytes, words, doublewords and quadwords) and numeric interpretations of fundamental data types for use in packed integer and packed floating point operations.

The 64-bit SIMD data types are operated on primarily in the 64-bit multimedia extension registers 58. The fundamental 64-bit packed data types are packed bytes, packed words and packed doublewords. When performing numeric SIMD operations on these data types in multimedia extension registers 58, these data types are interpreted as containing bytes, words, or doubleword integer values.

The 128-bit packed SIMD data types are operated on primarily in the 128-bit extended multimedia (XMM) registers 84 and memory 54. The fundamental 128-bit packed data types are packed bytes, packed words, packed doublewords and packed quadwords. When performing SIMD operations on these fundamental data types in extended multimedia (XMM) registers 84, these data types are interpreted as containing packed or scaler single precision floating point or double precision floating point values, or as containing packed byte, word, doubleword, quadword integer values.

FIG. 6 illustrates operations that may be performed by executing the MOVDDUP, MOVSHDUP, or MOVSLDUP instructions, according to one embodiment.

Referring to FIG. 5, a table 120 shows a summary of the various SIMD extensions, the data types operated on, and how the data types are packed into multimedia extension registers 58 and extended multimedia (XMM) registers 84.

As described above, multimedia extension instructions operate on packed byte, word, doubleword or quadword integer operands contained in memory 54, in multimedia extension registers 58, and/or in the general purposes registers 62. The multimedia extension instructions include data transfer instructions, conversion instructions, packed arithmetic instructions, comparison instructions, logical instructions, shift and rotate instructions and state management instructions.

SIMD extension (SSE and SSE2) instructions are divided into a number, e.g., four groups: SIMD single-precision floating point instructions that operate on the extended multimedia (XMM) registers 84, MXSCR instructions that operate on the MXCSR register 86, 64-bit SIMD integer instructions that operate on the MXX registers 58, and cacheability control, prefetch and instruction ordering instructions.

One class of instructions is move/load and duplicate-type instructions. These instructions are referred to as “combined” instructions in that they save the need to do an explicit operation on the value loaded to get, for example, duplication of bits. The present architecture includes a MOVDDUP instruction, a MOVSHDUP instruction and a MOVSLDUP instruction. These instructions are provided to support complex arithmetic with packed single and packed double-precision floating point data types. These instructions can be used in various applications. For example, these instructions can improve the efficiency of signal processing applications and applications that involve processing natural data types.

The MOVDDUP instruction is move one double-floating point and duplicate SSE2 instruction that loads/moves 64-bits (bits[63-0] if the source is a register). Execution of the MOVDDUP instruction returns the same 64-bits in both the lower and upper halves of the same result register, that is, duplicating the 64-bits from the source. Thus, if the source has entries 1/0 the destination will have entries 1/0/1/0. The MOVEDDUP instruction has the following format:

MOVEDDUP destination, source

-   where the source operand is a memory location 54 or a second     extended multimedia (XMM) register 84 and the destination operand is     a first extended multimedia (XMM) register 84. The source contains a     double-floating point data type.

In operation, if the source operand is a memory address, bits [63-0] of the first extended multimedia (XMM) register are loaded with bits [63-0] of the memory address and bits [127-64] of the first extended multimedia (XMM) register are loaded with bits [63-0] of the memory location. If the source operand is a second extended multimedia (XMM) register, bits [63-0] of the first extended multimedia (XMM) register are set equal to bits [63-0] of the second extended multimedia (XMM) register and bits [127-64] of the first extended multimedia (XMM) register are set equal to bits [63-0] of the second extended multimedia (XMM) register.

The linear address corresponds to the address of the least-significant byte of the referenced memory data. When a memory address is indicated, the 16 bytes of data at the memory location are loaded or stored. When the register-register form of the operation is used, the content of the 128-bit source register is copied into the 128-bit destination register.

The MOVSHDUP instruction is a move packed single-floating point high and duplicate SSE2 instruction that loads/moves 128-bits and duplicates entries 1 and 3 in the resulting register. In the example of a 128-bit source register width, each entry is 32 bits. Specifically, with a source being 3/2/1/0 entries (0 being the low single-precision entry and 3 being the high single-precision entry), a result register after execution of the MOVSHDUP instruction will store entries 3 and 1 duplicated to provide entries 3/3/1/1. The MOVSHDUP has the following format:

MOVSHDUP destination, source

-   where the source operand represents a memory location 54 or a second     extended multimedia (XMM) register 84 and the destination operand is     a first extended multimedia (XMM) register 84. The source operand     has a packed single-floating point data type.

In operation, if the source operand is a memory address, bits [31-0] of the first extended multimedia (XMM) register are loaded with bits [63-32] of the memory address, bits 63-32 of the first extended multimedia (XMM) register are loaded with bits [63-32] of the memory address, bits 95-64 of the first extended multimedia (XMM) register are loaded with bits [127-96] of the memory address and bits 127-96 of the first extended multimedia (XMM) register are loaded with bits [127-96] of the memory address.

If the source operand is a second extended multimedia (XMM) register, bits [31-0] of the first extended multimedia (XMM) register are set equal to bits [63-32] of the second extended multimedia (XMM) register, bits [63-32] of the first extended multimedia (XMM) register are set equal to bits [83-32] of the second extended multimedia (XMM) register, bits [95-64] of the first extended multimedia (XMM) register are set equal to bits [127-96] of the second extended multimedia (XMM) register, and bits [127-96] of the first extended multimedia (XMM) register are set equal to bits [127-96] of the second extended multimedia (XMM) register.

The linear address corresponds to the address of the least-significant byte of the referenced memory data. When a memory address is indicated, the 16 bytes of data at the memory location are loaded or stored. When the register-register form of the operation is used, the content of the 128-bit source register is copied into the 128-but destination register.

The MOVSLDUP instruction is a move packed single-floating point low and duplicate SSE2 instruction that loads/moves 128-bits and duplicates entries 0 and 2. Specifically, with a source being 3/2/1/0 (0 being the lower single-precision entry), a result register will store entries 2/2/0/0. The MOVSLDUP instruction has the following format:

MOVSLDUP destination, source

-   where the source operand is a memory location 54 or a second     extended multimedia (XMM) register 84 and the destination operand is     a first extended multimedia (XMM) register 84. The source operand     contains a packed single-floating point data type.

In operation, if the source operand is memory address, bits [31-0] of the first extended multimedia (XMM) register are loaded with bits [31-0] of the memory address, bits [63-32] of the first extended multimedia (XMM) register are loaded with bits [31-0] of the memory address, bits [95-64] of the first extended multimedia (XMM) register are loaded with bits [95-64] of the memory address and bits [127-96] of the first extended multimedia (XMM) register are loaded with bits [95-64] of the memory address. If the source operand is a register, bits [31-0] of the first extended multimedia (XMM) register are set equal to bits [31-0] of the second extended multimedia (XMM) register, bits [63-32] of the first extended multimedia (XMM) register are set equal to bits [31-0] of the second extended multimedia (XMM) register, bits [95-64] of the first extended multimedia (XMM) register are set equal to bits [95-64] of the second extended multimedia (XMM) register and bits [127-96] of the first extended multimedia (XMM) register are set equal to bits [95-64] of the second extended multimedia (XMM) register.

The linear address corresponds to the address of the least-significant byte of the referenced memory data. When a memory address is indicated, the 16 bytes of data at the memory location are loaded or stored. When the register-register form of the operation is used, the content of the 128-bit source register is copied into the 128-but destination register.

Accordingly, other embodiments are within the scope of the following claims. 

1. A processor comprising: a register to store a source operand; a core coupled with the register, the core in response to an instruction, which indicates the source operand and a destination operand, to store non-adjacent floating point values of the source operand, which are not explicitly specified by the instruction, into a first plurality of non-adjacent floating point values of the destination operand and to store duplicates of the non-adjacent floating point values of the source operand into a second plurality of non-adjacent floating point values of the destination operand, the first plurality of floating point values of the destination operand being stored adjacent to the second plurality of floating point values of the destination operand.
 2. The processor of claim 1, wherein the non-adjacent floating point values of the source operand are fixed by an opcode of the instruction.
 3. The processor of claim 1, wherein the instruction implicitly indicates the non-adjacent floating point values of the source operand.
 4. The processor of claim 1, wherein the instruction does not explicitly specify an order of the values in the destination operand.
 5. The processor of claim 1, wherein an opcode of the instruction indicates which values of the source operand are to appear in the destination operand.
 6. The processor of claim 1, wherein the instruction has a format comprising operand indication fields consisting of a first field to indicate the source operand and a second field to indicate the destination operand.
 7. The processor of claim 1, wherein all values of the destination operand are loaded, moved, or duplicated from the source operand.
 8. The processor of claim 1, wherein the floating point values of the source operand are single precision floating point values.
 9. A processor comprising: a register to store a source operand; a core coupled with the register, the core in response to an instruction, which indicates the source operand and a destination operand, to store non-adjacent floating point values of the source operand, which are implicit to an opcode of the instruction, into a first plurality of non-adjacent floating point values of the destination operand and to store duplicates of the non-adjacent floating point values of the source operand into a second plurality of non-adjacent floating point values of the destination operand, the first plurality of floating point values of the destination operand being stored adjacent to the second plurality of floating point values of the destination operand.
 10. The processor of claim 9, wherein the non-adjacent floating point values of the source operand are fixed by the opcode of the instruction.
 11. The processor of claim 9, wherein the instruction does not explicitly specify an order of the values in the destination operand.
 12. The processor of claim 9, wherein the instruction has a format comprising operand indication fields consisting of a first field to indicate the source operand and a second field to indicate the destination operand.
 13. The processor of claim 9, wherein all values of the destination operand are loaded, moved, or duplicated from the source operand.
 14. The processor of claim 9, wherein the floating point values of the source operand are single precision floating point values.
 15. A processor comprising: a plurality of registers; and a core coupled with the registers, the core operable in response to an instruction indicating a source operand and a destination register to: store a first packed data value of the source operand into a first packed data value of the destination register and a second packed data value of the destination register; and store a second packed data value of the source operand into a third packed data value of the destination register and a fourth packed data value of the destination register, wherein a third packed data value of the source operand between the first and second packed data values of the source operand is stored in the destination register.
 16. The processor of claim 15, wherein the first packed data value of the source operand comprises bits [63-32] of the source operand, the first packed data value of the destination register comprises bits [31-0] of the destination register, and the second packed data value of the destination register comprises bits [63-32] of the destination register, the second packed data value of the source operand comprises bits [127-96] of the source operand, the third packed data value of the destination register comprises bits [95-64] of the destination register, and the fourth packed data value of the destination register comprises bits [127-96] of the destination register.
 17. The processor of claim 15, wherein the first packed data value of the source operand comprises bits [31-0] of the source operand, the first packed data value of the destination register comprises bits [31-0] of the destination register, and the second packed data value of the destination register comprises bits [63-32] of the destination register, the second packed data value of the source operand comprises bits [95-64] of the source operand, the third packed data value of the destination register comprises bits [95-64] of the destination register, and the fourth packed data value of the destination register comprises bits [127-96] of the destination register.
 18. The processor of claim 15, wherein the first packed data value of the source operand comprises a floating point value.
 19. The processor of claim 15, wherein the instruction has a format comprising operand indication fields consisting of a first field to indicate the source operand and a second field to indicate the destination operand.
 20. The processor of claim 15, wherein all values of the destination register are loaded, moved, or duplicated from the source operand. 